fix(2): revert sealed batch if witness generation fails #5155
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix inconsistent state where a batch was sealed and stored but witness generation failed after #5152; in crates/l2/sequencer/l1_committer.rs wrap generate_and_store_batch_prover_input with error handling and call rollup_store.revert_to_batch(batch.number - 1) on failure to rollback the just-sealed batch, keeping DB and internal checkpoint state consistent; on success behavior is unchanged; consider future improvements like sealing only after witness generation or using a single transactional boundary for batch + witness persistence.
#5154